-
-
Notifications
You must be signed in to change notification settings - Fork 368
Prevent update_attributes from erasing all prior attributes #2870
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prevent update_attributes from erasing all prior attributes #2870
Conversation
| """ | ||
| # metadata.attributes is "frozen" so we simply clear and update the dict | ||
| self.metadata.attributes.clear() | ||
| self.metadata.attributes.update(new_attributes) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in principle we do want the metadata documents to be immutable, but as long as we are using plain python dicts for the attributes, immutability is not realistic. so updating in-place is fine.
dcherian
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. thanks
| >>> attrs | ||
| {'a': 3, 'c': 4} | ||
| """ | ||
| self._obj.metadata.attributes.clear() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a separate bug fix to the change in zarr/core/array.py? If so, it should get it's own changelog entry, and test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is to keep put (which formerly was using the undesired behavior in update_attributes) working as expected rather than a new feature or bugfix
This PR fixes attribute updating logic by clearing in calls to
putand removingclearcalls from allupdate_attributesmethods. It also fixes an apparent oversight in the JSON type (advise if I'm wrong) which didn't allow lists. Sequence should handle bothtupleandlistcloses: #2867
TODO:
docs/user-guide/*.rstchanges/